https://modernanalyst.com RSS feeds for Business Analyst Community & Resources | Modern Analyst 60 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6790/Top-7-Takeaway-Points-from-a-50-Year-Career-in-IT.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=6790 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6790&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6790/Top-7-Takeaway-Points-from-a-50-Year-Career-in-IT.aspx I measure the success of my 50+ year career in IT by the positive feedback I’ve received from colleagues, stakeholders, students, and readers. I started as a Cobol programmer, progressed to software analyst/designer, and for the last 30 years have performed the role of business analyst. Interspersed in those years I’ve shared what I’d learned through writing, teaching, presenting, and mentoring. This article discusses the top seven “Takeaway Points” from the over-30 BA resources I’ve produced related to requirements for information systems. adrian Sun, 08 Jun 2025 21:20:00 GMT f1397696-738c-4295-afcd-943feb885714:6790 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6429/Stuck-Going-in-Circles-Use-a-Circular-Flow-Diagram-CFD.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=6429 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6429&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6429/Stuck-Going-in-Circles-Use-a-Circular-Flow-Diagram-CFD.aspx In the intricate world of business analysis, understanding the complex interactions between various economic agents is crucial for making informed decisions. One tool that plays a pivotal role in comprehending these interactions is the Circular Flow Diagram or CFD. Originating from the field of economics, this visual representation has found its way into the toolkit of business analysts, offering a holistic view of how money, goods, and services circulate within a vertical industry or within an organization. In this article, we delve into the essence of the Circular Flow Diagram and explore its applications in the realm of business and systems analysis. adrian Sun, 21 Jan 2024 23:12:00 GMT f1397696-738c-4295-afcd-943feb885714:6429 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6259/Smart-Ideas-for-Effective-Business-Analysis-Documentation.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=6259 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6259&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6259/Smart-Ideas-for-Effective-Business-Analysis-Documentation.aspx Effective documentation is essential for successful business analysis, as it ensures that all stakeholders have a clear understanding of the goals, requirements, and processes. In addition, it helps identify potential risks and issues early on, so they can be addressed before they become major issues. It also allows  tracking changes and decisions over time. There are many kinds of documents business analysts create and maintain, including functional and non-functional requirement documents, release notes, design documents, feature overviews, process flow documents, etc. adrian Mon, 24 Apr 2023 00:30:00 GMT f1397696-738c-4295-afcd-943feb885714:6259 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6048/4-Diagrams-every-Analyst-should-Master.aspx#Comments 1 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=6048 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6048&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/6048/4-Diagrams-every-Analyst-should-Master.aspx A picture is worth a thousand words. Charts offer visualization and help to understand and comprehend things that would be more painful and time consuming to understand by reading free text. Diagrams help us design systems and processes, organize our screens, while facilitating a common understanding of the big picture. They help us make visible the invisible. Αs a BA you can exploit a big variety of diagrams to help you communicate better and more accurate information concerning the requirements and the solution. Diagrams leverages the effective use of visuals and modeling techniques in helping organizations and individuals work from the 30,000 foot view down to the level of detail that is needed by those who are actually going to perform the process activities. Moreover a diagram can serve as a single point of truth navigating what should be done and saving time from questions deriving from ambiguous point may found in a text. Transform VA Sun, 05 Jun 2022 04:32:00 GMT f1397696-738c-4295-afcd-943feb885714:6048 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5931/Design-Demands-Iteration.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=5931 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5931&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5931/Design-Demands-Iteration.aspx There’s always more than one design solution for a software problem and seldom a single best solution. The first design approach you conceive won’t be the best option. As one experienced designer explained it: You haven’t done your design job if you haven’t thought of at least three solutions, discarded all of them because they weren’t good enough, and then combined the best parts of all of them into a superior fourth solution. Sometimes, after considering three options, you realize that you don’t really understand the problem. Transform VA Sun, 03 Oct 2021 07:26:00 GMT f1397696-738c-4295-afcd-943feb885714:5931 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5912/Selecting-and-Tailoring-Business-Analysis-Approaches-Techniques.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=5912 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5912&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5912/Selecting-and-Tailoring-Business-Analysis-Approaches-Techniques.aspx It is true that a structural element of the conceptual framework of the BABOK knowledge areas is tailoring. The philosophy that a specific sequential approach does not fit in all circumstances is clear across all the knowledge areas and techniques presented. A business analyst has to critically filter and pick up the most useful techniques and approaches given the specific circumstances. Transform VA Sun, 19 Sep 2021 06:57:00 GMT f1397696-738c-4295-afcd-943feb885714:5912 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5874/Models-And-Diagrams-What-Is-The-Difference.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=5874 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5874&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5874/Models-And-Diagrams-What-Is-The-Difference.aspx A diagram is a 2-dimensional representation of a story, which shows elements and their relationships on a single canvas. An element is shown on a single diagram. (To show the same element information on a 2 diagrams, the element is duplicated.) When the properties of a diagram element are changed, the change is reflected only on that diagram. A model is a 3-dimensional representation of a collection of related stories, which captures diagram elements as model components. A component includes all element properties and relationships between different elements on all diagrams. A single model component can be shown as elements on several diagrams. A change to the properties of a diagram element or model component is reflected on every diagram where that component is displayed. A model does not necessarily need to include any diagrams. Diagramming is the most common method for creating and maintaining model components, but the diagrams can be deleted without changing the model. If a picture is worth a thousand words, then a diagram converts those words into a story. A model organizes those stories into a book. Transform VA Mon, 05 Jul 2021 17:54:00 GMT f1397696-738c-4295-afcd-943feb885714:5874 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5347/Requirements-In-Context-Part-3-Scope-High-Level-Requirements.aspx#Comments 3 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=5347 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5347&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5347/Requirements-In-Context-Part-3-Scope-High-Level-Requirements.aspx Project Scope. We will see how scope statements, when making reference to business functionality, lead directly to High-Level requirements.  Gathering requirements for a business information system is most often done within the context of a project. Approval of a project includes its sponsors signing off on its scope. The scope for a business information system project is typically defined in functional terms. Items in scope make reference to (or should make reference to) business functions, processes and/or activities that are to be delivered. adrian Sun, 05 May 2019 20:46:00 GMT f1397696-738c-4295-afcd-943feb885714:5347 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3747/Crossing-the-Imaginary-Line--Design-Thinking-in-Business-Analysis.aspx#Comments 4 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=3747 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3747&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/3747/Crossing-the-Imaginary-Line--Design-Thinking-in-Business-Analysis.aspx I take the approach that as Business Analysts, the line between requirements and design is an imaginary line. We need to be pragmatic (abandon purist thinking) and not be afraid to wear the design cloak, to adopt design thinking.    So how do we incorporate design thinking in Business Analysis in a value-add way? Take the following thoughts into consideration when working on your next project that involves building or significantly updating a customer-centric application. Author: Michael Roy, Business Analysis Professional / Requirements Leader Michael is a solutions-focused Business Analysis professional with extensive experience leading change initiatives at a tactical and strategic level.   michael_r_roy01 Sun, 04 Jun 2017 15:50:00 GMT f1397696-738c-4295-afcd-943feb885714:3747 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2945/Managing-the-Two-Sides-of-Decision-Modeling-Science-and-Art.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=2945 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2945&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2945/Managing-the-Two-Sides-of-Decision-Modeling-Science-and-Art.aspx In the real world, good decision modeling is always a balance between science and art. The science is systematic decomposition of a structure (of data or logic) into a set of smaller structures based on the definitions of successive normal forms. The art, on the other hand, is a general decomposition into a set of smaller structures based on factors not related to detecting and correcting normalization errors. Transform VA Mon, 28 Apr 2014 06:45:00 GMT f1397696-738c-4295-afcd-943feb885714:2945 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2008/Data-Modeling-Entity-Relationship-Diagram-ER-Diagram.aspx#Comments 1 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=2008 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2008&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2008/Data-Modeling-Entity-Relationship-Diagram-ER-Diagram.aspx This article describes the Entity Relationship Diagram that allows you to document the structure of a database in terms of persistent entities and the relationships between them.  The Entity-Relationship Diagram (ERD) provides a way of graphically representing the logical relationships between entities in order to create a database schema to persist those entities. speeditonline Mon, 25 Feb 2013 09:48:00 GMT f1397696-738c-4295-afcd-943feb885714:2008 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2009/An-Introduction-to-Data-Flow-Diagrams.aspx#Comments 8 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=2009 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2009&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2009/An-Introduction-to-Data-Flow-Diagrams.aspx A data flow diagram (commonly abbreviated to DFD) shows what information is needed within a process, where it is stored, and how it moves through a system to accomplish an objective. As its name implies, a data flow diagram depicts the flow of data within a system. speeditonline Mon, 23 Jan 2012 05:07:00 GMT f1397696-738c-4295-afcd-943feb885714:2009 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2015/Data-Flow-Diagram-with-Examples-Tips.aspx#Comments 6 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=2015 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2015&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2015/Data-Flow-Diagram-with-Examples-Tips.aspx  The Data Flow Diagram (DFD) provides a graphical representation of the flow of data through a system. It shows logically what information is exchanged by our system processes and external interfaces or data stores, but it does not explicitly show when or in what sequence the information is exchanged. speeditonline Mon, 10 Oct 2011 07:38:00 GMT f1397696-738c-4295-afcd-943feb885714:2015 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2012/Putting-Systems-Analysis-Into-Context-using-the-Context-Diagram.aspx#Comments 1 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=2012 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2012&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/2012/Putting-Systems-Analysis-Into-Context-using-the-Context-Diagram.aspx This article is all about putting your systems analysis into context; literally and metaphorically. It’s all about drawing and interpreting the not-quite-UML Context Diagram that is sometimes referred to as the System Context Diagram. speeditonline Tue, 20 Sep 2011 00:48:00 GMT f1397696-738c-4295-afcd-943feb885714:2012 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1552/Three-Types-of-Design-Effort.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=1552 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1552&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1552/Three-Types-of-Design-Effort.aspx In I.T., are we really spending too much time on "maintenance"?  Within any systems development organization, there are but three types of work effort: new systems development, maintenance, and modification/improvements. A mature development organization will spend approximately 5% of its time on new development, 10% on maintenance, and 85% of its time on modification/improvements. timbryce Sat, 18 Sep 2010 16:32:00 GMT f1397696-738c-4295-afcd-943feb885714:1552 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1355/Introduction-to-Context-Diagrams.aspx#Comments 4 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=1355 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1355&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1355/Introduction-to-Context-Diagrams.aspx Context diagrams are instrumental in unearthing unknown requirements during the discovery phase, both by forcing an analyst to think through the context (thus the moniker context diagram) of a project methodically and by enabling stakeholders to do so as well. Sun, 13 Jun 2010 04:10:00 GMT f1397696-738c-4295-afcd-943feb885714:1355 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1056/Information-Systems-Theory-101.aspx#Comments 1 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=1056 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1056&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/1056/Information-Systems-Theory-101.aspx Systems work is not as hard as you might think. However, we have a tendency in this business to complicate things by changing the vocabulary of systems work and introducing convoluted concepts and techniques, all of which makes it difficult to produce systems in a consistent manner. Consequently, there is a tendency to reinvent the wheel with each systems development project. I believe I owe it to my predecessors and the industry overall to describe basic systems theory, so that people can find the common ground needed to communicate and work. Fortunately, there are only four easy, yet important, concepts to grasp which I will try to define as succinctly as possible. timbryce Thu, 20 Aug 2009 04:01:00 GMT f1397696-738c-4295-afcd-943feb885714:1056 https://modernanalyst.com/Resources/Articles/tabid/115/ID/592/Stakeholder-Communications--Pictures-not-Words.aspx#Comments 5 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=592 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=592&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/592/Stakeholder-Communications--Pictures-not-Words.aspx Many people on our Business Analysis workshop ask why we use dataflow diagrams (DFDs). Why not Use Case…or even BPMN? After all DFDs have been around for 20 years, surely the world has moved on? Well, has it? The primary purpose of a business analyst is to communicate – to stakeholders and to solution providers – and when it comes to communication we all know that pictures (diagrams) are much more effective and less ambiguous than words. Remember the phrase "A picture is worth a thousand words". The question is – which type of diagram best suits our needs? In this article, written by IRM's Training Services Manager Jan Kusiak, we’ll look at using diagrams for stakeholder communications. Author: Jan Kusiak pddean Sat, 01 Nov 2008 00:37:00 GMT f1397696-738c-4295-afcd-943feb885714:592 https://modernanalyst.com/Resources/Articles/tabid/115/ID/463/Eight-Competencies-a-Business-Analyst-Needs-to-Know.aspx#Comments 12 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=463 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=463&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/463/Eight-Competencies-a-Business-Analyst-Needs-to-Know.aspx Failing to properly and accurately define requirements at the very beginning of the project lifecycle points to a distinct lack of business analysis competency. The role of the business analyst is an important one, and, sadly, one that is underutilized by many organizations around the world. In essence, a business analyst acts as a translator or liaison between the customer or user and the person or group attempting to meet user needs. But, that’s just speaking generally. What about the specifics? Below, I’ve put together a list of eight key competencies that every business analyst—or every professional performing the duties of a business analyst—should possess. I’ve included specific emphasis on tasks associated with junior, intermediate and senior business analysts. If performed effectively, the items on this list could save organizations millions. adrian Tue, 08 Jul 2008 02:30:00 GMT f1397696-738c-4295-afcd-943feb885714:463 https://modernanalyst.com/Resources/Articles/tabid/115/ID/242/A-Short-History-of-Systems-Development.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=242 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=242&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/242/A-Short-History-of-Systems-Development.aspx I have been very fortunate to see a lot of this history first hand. I have observed changes not just in terms of systems and computers, but also how the trade press has evolved and the profession in general. It has been an interesting ride. Throughout all of this, there have been some very intelligent people who have impacted the industry, there have also been quite a few charlatans, but there has only been a handful of true geniuses, one of which was Robert W. Beamer who passed away just a couple of years ago. Bob was the father of ASCII code, without which we wouldn't have the computers of today, the Internet, the billions of dollars owned by Bill Gates, or this document. I always find it amusing when I tell a young person in this industry that I worked with punch cards and plastic templates years ago. Its kind of the same dumbfounded look I get from my kids when I tell them we used to watch black and white television with three channels, no remote control, and station signoffs at midnight. It has been my observation that our younger workers do not have a sense of history; this is particularly apparent in the systems world. If they do not have an appreciation of whence we came, I doubt they will have an appreciation of where we should be going. Consequently, I have assembled the following chronology of events in the hopes this will provide some insight as to how the systems industry has evolved to its current state. I'm sure I could turn this into a lengthy dissertation but, instead, I will try to be brief and to the point. Further, the following will have little concern for academic developments but rather how systems have been implemented in practice in the corporate world. timbryce Mon, 04 Feb 2008 15:55:00 GMT f1397696-738c-4295-afcd-943feb885714:242 https://modernanalyst.com/Resources/Articles/tabid/115/ID/198/Functional-Specification--a-Tutorial.aspx#Comments 2 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=198 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=198&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/198/Functional-Specification--a-Tutorial.aspx What Is A Functional Specification? Functional specifications (functional specs), in the end, are the blueprint for how you want a particular web project or application to look and work. It details what the finished product will do, how a user will interact with it, and what it will look like. By creating a blueprint of the product first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect. Why write a Functional Spec? A key benefit of writing up a Functional Spec is in streamlining the development process. The developer working from the spec has, ideally, all of their questions answered about the application and can start building it. And since this is a spec that was approved by the client, they are building nothing less than what the client is expecting. There should be nothing left to guess or interpret when the spec is completed...and this, in a nut, explains my love affair with the Functional Spec. Who writes a Functional Spec? The functional spec should be written by someone who is not involved in any other aspect of the project. You will want somebody who is very familiar with user-interface issues and web design, familiar enough with technology to know its limitations and capabilities, and someone who is a very skilled and detailed writer. While writing a spec, you will spend much of your time imagining how a user might use a certain feature and how they may navigate their way through the information. Not only do you need to map this world out visually, but you also have to write out in great detail what this world does; all the while, balancing everything within the current technological limitations and business demands. The functional spec writer's sole concern is marrying the user-experience with the various departmental, business, and technical requirements of the project.  Author: Allen W. Smith adrian Sun, 02 Dec 2007 06:18:00 GMT f1397696-738c-4295-afcd-943feb885714:198 https://modernanalyst.com/Resources/Articles/tabid/115/ID/168/From-Use-Case-Diagrams-to-Context-Diagrams.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=168 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=168&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/168/From-Use-Case-Diagrams-to-Context-Diagrams.aspx As long as practitioners recognize that use case diagrams are optional and iconic (as opposed to schematic), they shouldn't have problems. The diagrams are useful, for example, on whiteboards as a way of sketching and framing an agenda while people are writing up and reviewing use case detail on index cards. The trouble starts, however, when projects end up with unreadable and overly complex use case diagrams. Those diagrams distract project members from the more useful endeavor of elaborating the use cases and result in wasted time. And the major value of the use case diagram -- showing the context of a software system -- ends up lost in a cloud of bubbles. Author: Kevlin Henney admin Sat, 03 Nov 2007 05:48:00 GMT f1397696-738c-4295-afcd-943feb885714:168 https://modernanalyst.com/Resources/Articles/tabid/115/ID/7/Analysis-and-Design-Considered-Harmful.aspx#Comments 2 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=7 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/7/Analysis-and-Design-Considered-Harmful.aspx This article describes a common pitfall of thinking of analysis and design together as a single process, and highlights the need to treat analysis and design as two separate processes. The author, points out that much of the UML standard, as it is explained today, is described in terms of design artifacts rather than analysis artifacts. Author: Conrad Weisert cadams5 Wed, 01 Aug 2007 17:14:00 GMT f1397696-738c-4295-afcd-943feb885714:7 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5/Implicit-Data-Dictionaries-are-Dangerous.aspx#Comments 0 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=5 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/5/Implicit-Data-Dictionaries-are-Dangerous.aspx Describes the difference between a data dictionary and an implicit data dictionary and why an implicit data dictionary (or no data dictionary at all) may spell trouble for your project. Can data dictionaries be used with UML Use Cases or an XP methodology? Author: Conrad Weisert cadams5 Wed, 01 Aug 2007 16:34:00 GMT f1397696-738c-4295-afcd-943feb885714:5 https://modernanalyst.com/Resources/Articles/tabid/115/ID/65/Separating-Analysis-from-Design.aspx#Comments 1 https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&ModuleID=572&ArticleID=65 https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=65&PortalID=0&TabID=115 https://modernanalyst.com/Resources/Articles/tabid/115/ID/65/Separating-Analysis-from-Design.aspx "Business Analysis is about thinking what your solution should do, while Design is about how to make it happen using the technology available. Don't ever combine the two - you save nothing." This paper by Brian Cooney, principal instructor at IRM, describes the need for clear separation between the two phases and the benefits this provides for a successful project outcome. Author: Brian Cooney adrian Mon, 02 Jul 2007 19:58:00 GMT f1397696-738c-4295-afcd-943feb885714:65